<?xml version="1.0" encoding="UTF-8"?>
<html filename="docs/SAX/IErrorHandler.html">
<body>
<a id="#top"/>
<h1>
	                Interface Summary : IErrorHandler </h1> Basic interface for SAX error handlers.

 <blockquote>
 <em>This module, both source code and documentation, is in the
 Public Domain, and comes with <strong>NO WARRANTY</strong>.</em>
 </blockquote>

 <p>If a SAX application needs to implement customized error
 handling, it must implement this interface and then register an
 instance with the XML reader using the
 <a href="../SAX/IXMLReader.html#setErrorHandler">setErrorHandler</a>
 method.  The parser will then report all errors and warnings
 through this interface.</p>

 <p>
      <strong>WARNING:</strong> If an application does <em>not</em>
 register an ErrorHandler, XML parsing errors will go unreported,
 except that <em>ESAXParseException</em>s will be thrown for fatal errors.
 In order to detect validity errors, an ErrorHandler that does something
 with <a href="../SAX/IErrorHandler.html#error">error</a> calls must be registered.</p>

 <p>For XML processing errors, a SAX driver must use this interface
 in preference to throwing an exception: it is up to the application
 to decide whether to throw an exception for different types of
 errors and warnings.  Note, however, that there is no requirement that
 the parser continue to report additional errors after a call to
 <a href="../SAX/IErrorHandler.html#fatalError">fatalError</a>.  In other words, a SAX driver class
 may throw an exception after reporting any fatalError. 
 Also parsers may throw appropriate exceptions for non-XML errors.
 For example, <a href="../SAX/IXMLReader.html#parse">IXMLReader.parse</a> would throw
 an Exception for errors accessing entities or the document.</p>

 <p>SAX for Pascal does not follow the model of SAX for Java. To
 better manage the life-cycle of errors, the ISAXError interface
 was developed. For more information on errors in SAX for pascal
 see <a href="../SAX/ISAXError.html">ISAXError</a></p>

<br/><b>Since : </b> SAX 1.0
<br/><b>See : </b> <a href="../SAX/IXMLReader.html#setErrorHandler">IXMLReader.setErrorHandler</a>
<br/><b>See : </b> <a href="../SAX/ESAXParseException.html">ESAXParseException</a>
<h2>
	              Methods
	            </h2>
<div style="padding-left:10px">
<a href="#warning">
	                  procedure
	                 warning(ISAXParseError)</a>
<br/>
<a href="#error">
	                  procedure
	                 error(ISAXParseError)</a>
<br/>
<a href="#fatalError">
	                  procedure
	                 fatalError(ISAXParseError)</a>
<br/>
</div>
<br/>
<hr width="100%"/>
<a name="#warning">
<p>
<b>procedure</b> warning(<b>const</b> e : ISAXParseError); </p>
</a> Receive notification of a warning.

 <p>SAX parsers will use this method to report conditions that
 are not errors or fatal errors as defined by the XML 1.0
 recommendation.  The default behaviour is to take no action.</p>

 <p>The SAX parser must continue to provide normal parsing events
 after invoking this method: it should still be possible for the
 application to process the document through to the end.</p>

 <p>Filters may use this method to report other, non-XML warnings
 as well.</p>

<br/><b>Parameter : </b> e The warning information encapsulated in a
          SAX parse error interface.
<br/><b>See : </b> <a href="../SAX/ISAXParseError.html">ISAXParseError</a>
<br/>
<p>
<a href="#top">Top</a>
</p>
<hr width="100%"/>
<a name="#error">
<p>
<b>procedure</b> error(<b>const</b> e : ISAXParseError); </p>
</a> Receive notification of a recoverable error.

 <p>This corresponds to the definition of &quot;error&quot; in section 1.2
 of the W3C XML 1.0 Recommendation.  For example, a validating
 parser would use this callback to report the violation of a
 validity constraint.  The default behaviour is to take no
 action.</p>

 <p>The SAX parser must continue to provide normal parsing events
 after invoking this method: it should still be possible for the
 application to process the document through to the end.  If the
 application cannot do so, then the parser should report a fatal
 error even if the XML 1.0 recommendation does not require it to
 do so.</p>

 <p>Filters may use this method to report other, non-XML errors
 as well.</p>

<br/><b>Parameter : </b> e The error information encapsulated in a
          SAX parse error interface.
<br/><b>See : </b> <a href="../SAX/ISAXParseError.html">ISAXParseError</a>
<br/>
<p>
<a href="#top">Top</a>
</p>
<hr width="100%"/>
<a name="#fatalError">
<p>
<b>procedure</b> fatalError(<b>const</b> e : ISAXParseError); </p>
</a> Receive notification of a non-recoverable error.

 <p>This corresponds to the definition of &quot;fatal error&quot; in
 section 1.2 of the W3C XML 1.0 Recommendation.  For example, a
 parser would use this callback to report the violation of a
 well-formedness constraint.</p>

 <p>The application must assume that the document is unusable
 after the parser has invoked this method, and should continue
 (if at all) only for the sake of collecting additional error
 messages: in fact, SAX parsers are free to stop reporting any
 other events once this method has been invoked.</p>

<br/><b>Parameter : </b> e The error information encapsulated in a
          SAX parse error interface.
<br/><b>See : </b> <a href="../SAX/ISAXParseError.html">ISAXParseError</a>
<br/>
<p>
<a href="#top">Top</a>
</p>
</body>
</html>